Skip to content

Conversation

@jip149
Copy link

@jip149 jip149 commented Oct 3, 2025

Proposed Changes

HelmController fails on bootstrap charts when the API server is not listening on port 127.0.0.1:6443.

A PR has been submitted to fix this issue: k3s-io/helm-controller#288

The PR changes the chart.Register function signature, and this change needs to be reflected in k3s.

This will also avoid breaking bootstrap charts if some day k3s is updated not to forcefully listen on 127.0.0.1

Types of Changes

This basically just adds an argument to function call.

Verification

curl -sfL https://get.k3s.io | sh -s - server --cluster-cidr=2001:db8:42::/56 --service-cidr=2001:db8:43::/112 --flannel-ipv6-masq
kubectl apply -f - <<EOF
apiVersion: v1
kind: Namespace
metadata:
  name: web
---
apiVersion: helm.cattle.io/v1
kind: HelmChart
metadata:
  name: apache
  namespace: kube-system
spec:
  repo: https://charts.bitnami.com/bitnami
  chart: apache
  bootstrap: true
  targetNamespace: web
  valuesContent: |-
    service:
      type: ClusterIP
    ingress:
      enabled: true
      hostname: www.example.com
    metrics:
      enabled: true
EOF

Chart should install without error.

Testing

An issue is open #12991

Linked Issues

See discussion here #12947

User-Facing Change

NONE

jip149 added 2 commits October 3, 2025 10:29
The default API server bind address was determined when starting the API
server but was not stored anywhere.

It can be useful to get access to the address later on, so we instead
store the default value as if it had been given in the configuration.
HelmController needs API server address for bootstrap charts
@jip149 jip149 requested a review from a team as a code owner October 3, 2025 12:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant